← previous blocknext block →recent activity
Analyzing
Block #87,617,069
15 transactions · 13 stateful · 2026-07-14 03:14:38 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,617,069 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w29w211w112w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca3f1796…927c
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x2c53a187…3646
0x34b655…2a6f
4 touches
1 conflict
0x46d5a052…ff2e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56091b00…b694
0x34b655…2a6f
4 touches
1 conflict
0x59a5e379…ad8e
0x34b655…2a6f
4 touches
1 conflict
0x59a5e379…ad8f
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xca3f1796b4…ff927c
Audit this contract →
← previous block·next block →recent activity