← previous blocknext block →recent activity
Analyzing
Block #83,495,008
10 transactions · 9 stateful · 2026-06-25 00:45:33 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,495,008 · 10 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
1w02w13w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa215fe48…3330
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa02e5cdd…76b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1ed7bc2d…93eb
0x065c9d…c394
2 touches
0 conflicts
0x38e073fe…1e51
0x065c9d…c394
2 touches
0 conflicts
0xf6a0c317…855d
0x065c9d…c394
2 touches
0 conflicts
0x226b141d…1864
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 0xa215fe48c1…af3330
Audit this contract →
← previous block·next block →recent activity