← previous blocknext block →recent activity
Analyzing
Block #85,197,232
16 transactions · 16 stateful · 2026-07-02 21:56:03 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,197,232 · 16 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
2w03w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0x36d04d61…ee9d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x925affea…49da
0x34b655…2a6f
4 touches
1 conflict
0x06f0d2ab…dd75
0x34b655…2a6f
2 touches
0 conflicts
0x09ce76d1…b412
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x2c2d08d5…089f
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 0xd63e616b67…7fa07d
Audit this contract →
← previous block·next block →recent activity