← previous blocknext block →recent activity
Analyzing
Block #84,460,862
30 transactions · 26 stateful · 2026-06-29 12:04:31 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,460,862 · 30 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
2w04w05w16w08w19w010w111w112w013w115w016w118w021w222w323w226w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
6 touches
3 conflicts
0x753f76d0…5199
0x34b655…2a6f
4 touches
1 conflict
0x807bf45f…5016
0x34b655…2a6f
4 touches
1 conflict
0x8802094b…3402
0x34b655…2a6f
4 touches
1 conflict
0xa315ce38…44ce
0x34b655…2a6f
4 touches
1 conflict
0xa37d59c6…996b
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity