← previous blocknext block →recent activity
Analyzing
Block #83,630,007
15 transactions · 13 stateful · 2026-06-25 15:46:23 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,630,007 · 15 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
1w04w05w17w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049cca71…b102
0x34b655…2a6f
4 touches
1 conflict
0x06ce36d6…937d
0x34b655…2a6f
4 touches
1 conflict
0x5396d712…a139
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0xbb3504d4…b05f
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0xac28fe82…4f8e
0x065c9d…c394
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 0x049cca710d…16b102
Audit this contract →
← previous block·next block →recent activity