← previous blocknext block →recent activity
Analyzing
Block #83,639,721
13 transactions · 12 stateful · 2026-06-25 16:51:18 UTC
Parallelism
46/100
Blocked
58%
Avg conflicts / tx
1.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,639,721 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w38w49w511w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7468e81…86e5
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x7e6c970a…65af
0x34b655…2a6f
6 touches
3 conflicts
0x2aba97ba…7464
0x34b655…2a6f
6 touches
3 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
6 touches
3 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xf7468e81f0…5b86e5
Audit this contract →
← previous block·next block →recent activity