← previous blocknext block →recent activity
Analyzing
Block #84,354,323
13 transactions · 12 stateful · 2026-06-29 00:14:27 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,354,323 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c364015…c98f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xee7978e9…2869
0x34b655…2a6f
4 touches
1 conflict
0xbfe63d66…c3e6
0x34b655…2a6f
3 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
2 touches
0 conflicts
0xd72a1ce6…4b2f
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 0x6c364015e7…27c98f
Audit this contract →
← previous block·next block →recent activity