← previous blocknext block →recent activity
Analyzing
Block #80,822,180
22 transactions · 14 stateful · 2026-06-12 15:30:52 UTC
Parallelism
91/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,822,180 · 22 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
1w02w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1da1c6cb…bb3f
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
3 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
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 0x1da1c6cbeb…31bb3f
Audit this contract →
← previous block·next block →recent activity