← previous blocknext block →recent activity
Analyzing
Block #83,889,663
17 transactions · 17 stateful · 2026-06-26 20:38:55 UTC
Parallelism
88/100
Blocked
12%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,889,663 · 17 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
1w02w111w012w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x07abcd28…c699
0x40c49f…2af0
2 touches
0 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
2 touches
0 conflicts
0xc9576c5e…e9dc
0x40c49f…2af0
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 0x6b47245e5d…eda342
Audit this contract →
← previous block·next block →recent activity