← previous blocknext block →recent activity
Analyzing
Block #84,359,328
13 transactions · 11 stateful · 2026-06-29 00:47:51 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,359,328 · 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
1w02w05w08w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7534f53d…6ed4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xff4ee2c4…6e5e
0x34b655…2a6f
4 touches
1 conflict
0x8eb5f632…c9eb
0x34b655…2a6f
4 touches
1 conflict
0xda47a23d…57e3
0xa6afd3…d132
4 touches
1 conflict
0xac265060…146e
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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 0x7534f53d7a…5a6ed4
Audit this contract →
← previous block·next block →recent activity