← previous blocknext block →recent activity
Analyzing
Block #80,823,471
31 transactions · 23 stateful · 2026-06-12 15:39:28 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,823,471 · 31 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
2w03w14w25w07w18w214w015w117w018w119w226w027w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xde6b917f…3a72
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0x6fae99…a56d
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xaa6f28d9…83ef
0x34b655…2a6f
4 touches
1 conflict
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity