← previous blocknext block →recent activity
Analyzing
Block #87,716,912
25 transactions · 22 stateful · 2026-07-14 14:22:26 UTC
Parallelism
84/100
Blocked
55%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,716,912 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w08w112w113w215w016w117w118w219w323w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5c591136…d322
0x34b655…2a6f
6 touches
3 conflicts
0x8a1f78fd…b178
0x34b655…2a6f
6 touches
3 conflicts
0x0c50f178…20e0
0x34b655…2a6f
4 touches
1 conflict
0x2247808c…8735
0x34b655…2a6f
4 touches
1 conflict
0x226ae29a…2612
0x34b655…2a6f
4 touches
1 conflict
0x24121dfe…96e4
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 0x2385516f6a…9aeca5
Audit this contract →
← previous block·next block →recent activity