← previous blocknext block →recent activity
Analyzing
Block #83,455,694
10 transactions · 8 stateful · 2026-06-24 20:23:21 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,455,694 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d35e1ad…b4d6
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x2d95c7ff…1596
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x56877713…6a2f
0x34b655…2a6f
2 touches
0 conflicts
0x79e6f4db…b14a
0x34b655…2a6f
2 touches
0 conflicts
0x7b3a71df…68d7
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 0x0d35e1ad50…a7b4d6
Audit this contract →
← previous block·next block →recent activity