← previous blocknext block →recent activity
Analyzing
Block #87,699,419
14 transactions · 11 stateful · 2026-07-14 12:25:00 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,699,419 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w110w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa27f1875…0c5d
0x34b655…2a6f
6 touches
3 conflicts
0xbf546ab2…a777
0x34b655…2a6f
4 touches
1 conflict
0xc8dfd9a6…5b4e
0x34b655…2a6f
4 touches
1 conflict
0xf81d0d0f…cf78
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6628
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6629
0x34b655…2a6f
4 touches
1 conflict
0xa505051b…0632
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xa27f187578…2a0c5d
Audit this contract →
← previous block·next block →recent activity