← previous blocknext block →recent activity
Analyzing
Block #84,249,404
13 transactions · 13 stateful · 2026-06-28 12:35:22 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,249,404 · 13 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
2w03w04w15w07w18w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x1c524db7…4ac4
0x34b655…2a6f
2 touches
0 conflicts
0x200db05e…6327
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 0x90a9e3f873…9117ab
Audit this contract →
← previous block·next block →recent activity