← previous blocknext block →recent activity
Analyzing
Block #83,670,995
13 transactions · 12 stateful · 2026-06-25 20:19:55 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,670,995 · 13 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
2w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99ee776a…053a
0x34b655…2a6f
4 touches
1 conflict
0x68c6b2fa…098d
0x34b655…2a6f
4 touches
1 conflict
0x0c005790…6210
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x0f068b13…fb19
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x27d815d2…5ca9
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfa032…139c
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 0x99ee776a78…65053a
Audit this contract →
← previous block·next block →recent activity