← previous blocknext block →recent activity
Analyzing
Block #83,470,168
21 transactions · 15 stateful · 2026-06-24 22:00:00 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,470,168 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w012w113w217w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0720d2a9…57f6
0x34b655…2a6f
6 touches
3 conflicts
0xdb7c435f…f490
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x315bc463…8926
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
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 0x0720d2a9a0…2a57f6
Audit this contract →
← previous block·next block →recent activity