← previous blocknext block →recent activity
Analyzing
Block #83,583,392
15 transactions · 15 stateful · 2026-06-25 10:35:00 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,583,392 · 15 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
1w02w13w06w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x2274cf9c…3c78
0x34b655…2a6f
2 touches
0 conflicts
0x51a4d156…4e3e
0x34b655…2a6f
2 touches
0 conflicts
0xd026fe03…7748
0x34b655…2a6f
2 touches
0 conflicts
0xe64e6363…e676
0x34b655…2a6f
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity