← previous blocknext block →recent activity
Analyzing
Block #87,737,854
11 transactions · 11 stateful · 2026-07-14 16:42:31 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,737,854 · 11 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
1w03w04w15w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x47e6eaf7…65eb
0x34b655…2a6f
4 touches
1 conflict
0x2f4beec6…ab79
0x34b655…2a6f
4 touches
1 conflict
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8df5fa2c…02e6
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x08cc68a2c8…482a59
Audit this contract →
← previous block·next block →recent activity