← previous blocknext block →recent activity
Analyzing
Block #83,039,318
7 transactions · 4 stateful · 2026-06-22 22:00:41 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,039,318 · 7 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x97785d36…2ac5
0x34b655…2a6f
4 touches
1 conflict
0xb251976b…4938
0x34b655…2a6f
4 touches
1 conflict
0xd25a34fd…3e4d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x443d4ecd…741a
0x34b655…2a6f
4 touches
1 conflict
0x3330d5c8…3f94
0x34b655…2a6f
2 touches
0 conflicts
0x3e505a15…70f8
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 0x727fbce74b…da0c80
Audit this contract →
← previous block·next block →recent activity