← previous blocknext block →recent activity
Analyzing
Block #83,483,298
13 transactions · 12 stateful · 2026-06-24 23:27:33 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,483,298 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf1
0x34b655…2a6f
6 touches
3 conflicts
0x60872583…6452
0x34b655…2a6f
6 touches
3 conflicts
0xb99958f6…ccf0
0x34b655…2a6f
6 touches
3 conflicts
0x5dc2541c…dd2f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f068b13…fb19
0x34b655…2a6f
4 touches
1 conflict
0x1ab89a2a…b7b1
0x34b655…2a6f
4 touches
1 conflict
0xd8fd2add…50fc
0x69df8a…6292
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 0xb99958f6c8…c6ccf1
Audit this contract →
← previous block·next block →recent activity