← previous blocknext block →recent activity
Analyzing
Block #84,359,866
24 transactions · 17 stateful · 2026-06-29 00:51:27 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,359,866 · 24 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
1w02w16w28w311w012w013w115w116w017w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a5dd7b4…fba4
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xe02484a6…c32e
0xc8689a…ee79
4 touches
1 conflict
0x1ff965a5…b3aa
0x34b655…2a6f
4 touches
1 conflict
0x3187fda9…57d9
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 0x5a5dd7b4d7…36fba4
Audit this contract →
← previous block·next block →recent activity