← previous blocknext block →recent activity
Analyzing
Block #82,967,796
16 transactions · 14 stateful · 2026-06-22 14:01:57 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,967,796 · 16 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
2w014w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97785d36…2ac5
0x34b655…2a6f
4 touches
1 conflict
0xc9eaeefd…d5a3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeb6e68d3…5762
0x34b655…2a6f
4 touches
1 conflict
0x4fe95978…4ea7
0x34b655…2a6f
4 touches
1 conflict
0x6ccfa398…71a1
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x9975b329…d659
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
1 conflict on slot 0x97785d3608…432ac5
Audit this contract →
← previous block·next block →recent activity