← previous blocknext block →recent activity
Analyzing
Block #83,455,162
14 transactions · 10 stateful · 2026-06-24 20:19:47 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,455,162 · 14 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
6w07w18w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf37a93d…879b
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x5cc8dd43…8cf2
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x20e499f7…fa84
0x34b655…2a6f
4 touches
1 conflict
0x12e112ce…9a7d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xdf37a93d9a…3f879b
Audit this contract →
← previous block·next block →recent activity