← previous blocknext block →recent activity
Analyzing
Block #80,157,037
16 transactions · 12 stateful · 2026-06-09 13:35:27 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,157,037 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w113w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5ffc25fa…b119
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xb70a77d7…bf0a
0x34b655…2a6f
4 touches
1 conflict
0xc5dc29f0…f0c6
0x34b655…2a6f
4 touches
1 conflict
0xce7c598a…631b
0x34b655…2a6f
4 touches
1 conflict
0xd5dbfacf…c5ec
0x34b655…2a6f
4 touches
1 conflict
0x0462262d…a368
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity