← previous blocknext block →recent activity
Analyzing
Block #84,317,183
10 transactions · 8 stateful · 2026-06-28 20:06:51 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,317,183 · 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
1w02w15w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28a5dbb8…3ad7
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0x0833f1ab…71e7
0x34b655…2a6f
2 touches
0 conflicts
0x3f7ad3a0…de3b
0x34b655…2a6f
2 touches
0 conflicts
0x5e0d7b06…8054
0x34b655…2a6f
2 touches
0 conflicts
0x6acc4afc…e7db
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 0x28a5dbb865…4d3ad7
Audit this contract →
← previous block·next block →recent activity