← previous blocknext block →recent activity
Analyzing
Block #83,668,816
10 transactions · 8 stateful · 2026-06-25 20:05:23 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,668,816 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde696e46…6446
0x34b655…2a6f
6 touches
3 conflicts
0x732ec6a5…627a
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x913ebf0e…d816
0x34b655…2a6f
3 touches
1 conflict
0xb5b71470…8bb8
0x754704…b603
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
3 conflicts on slot 0xde696e4658…1e6446
Audit this contract →
← previous block·next block →recent activity