← previous blocknext block →recent activity
Analyzing
Block #83,639,728
18 transactions · 16 stateful · 2026-06-25 16:51:21 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,639,728 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w210w014w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e2262…cd8c
0x34b655…2a6f
6 touches
3 conflicts
0xd6d4eb00…30f3
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xf7468e81…86e5
0x34b655…2a6f
6 touches
3 conflicts
0x8b61212e…558e
0x34b655…2a6f
4 touches
1 conflict
0x96a35ba8…3d0c
0x34b655…2a6f
4 touches
1 conflict
0xa7344ade…a467
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