← previous blocknext block →recent activity
Analyzing
Block #83,455,517
25 transactions · 17 stateful · 2026-06-24 20:22:10 UTC
Parallelism
92/100
Blocked
12%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,455,517 · 25 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
1w02w113w018w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec06bf19…fcc3
0x34b655…2a6f
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0xeeffa323…34f7
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0xa8d86215…afa2
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0xd77e90ec…8c04
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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 0xec06bf1924…dffcc3
Audit this contract →
← previous block·next block →recent activity