← previous blocknext block →recent activity
Analyzing
Block #86,947,067
16 transactions · 13 stateful · 2026-07-11 00:33:55 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,947,067 · 16 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
1w02w14w05w16w08w19w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d1bb389…c7d9
0xb1dbf0…c0d3
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ad
0xb1dbf0…c0d3
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2d4406f9…a357
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: 0xb1dbf05f…b1c0d3
1 conflict on slot 0x9d1bb3891b…cac7d9
Audit this contract →
← previous block·next block →recent activity