← previous blocknext block →recent activity
Analyzing
Block #80,953,624
14 transactions · 9 stateful · 2026-06-13 06:07:25 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,953,624 · 14 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5588d596…55d9
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xd2dc9e94…00b3
0x34b655…2a6f
3 touches
1 conflict
0x2d118805…34a3
0x065c9d…c394
2 touches
0 conflicts
0x88b32975…1070
0x065c9d…c394
2 touches
0 conflicts
0x5581d709…ab77
0x2a68ba…90c5
2 touches
0 conflicts
0x23a320fb…cbd7
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 0x5588d5960d…5055d9
Audit this contract →
← previous block·next block →recent activity