← previous blocknext block →recent activity
Analyzing
Block #84,285,595
14 transactions · 14 stateful · 2026-06-28 16:36:29 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,285,595 · 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
6w07w08w09w010w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd63138b…63d9
0x34b655…2a6f
6 touches
3 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x1c1e591b…d93d
0x34b655…2a6f
4 touches
1 conflict
0x3405238a…68b6
0x34b655…2a6f
4 touches
1 conflict
0x564429c3…63a4
0x34b655…2a6f
4 touches
1 conflict
0xa80684c9…3948
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 0xcd63138b1f…b763d9
Audit this contract →
← previous block·next block →recent activity