← previous blocknext block →recent activity
Analyzing
Block #83,638,425
13 transactions · 11 stateful · 2026-06-25 16:42:40 UTC
Parallelism
54/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,638,425 · 13 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
1w05w16w27w38w411w012w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcde75077…ccee
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0x5277fe22…c910
0x34b655…2a6f
4 touches
1 conflict
0xa07d26c2…13bc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
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
6 conflicts on slot 0xcde75077a7…6dccee
Audit this contract →
← previous block·next block →recent activity