← previous blocknext block →recent activity
Analyzing
Block #85,194,120
16 transactions · 15 stateful · 2026-07-02 21:35:17 UTC
Parallelism
81/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,194,120 · 16 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
1w02w16w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x07b4e226…da90
0x40c49f…2af0
2 touches
0 conflicts
0x2959aa16…51be
0x40c49f…2af0
2 touches
0 conflicts
0x5b07cfe2…c0a0
0x40c49f…2af0
2 touches
0 conflicts
0xc644dfe2…dac9
0x40c49f…2af0
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 0x06aed19eee…1cca57
Audit this contract →
← previous block·next block →recent activity