← previous blocknext block →recent activity
Analyzing
Block #87,699,899
17 transactions · 16 stateful · 2026-07-14 12:28:13 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,699,899 · 17 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
1w04w05w16w27w310w111w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6419ef2…1643
0x34b655…2a6f
8 touches
6 conflicts
0x2e18cc5a…f631
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x54892787…0552
0x34b655…2a6f
4 touches
1 conflict
0x548b3085…91c0
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7252311d…d8cf
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
6 conflicts on slot 0xd6419ef238…5f1643
Audit this contract →
← previous block·next block →recent activity