← previous blocknext block →recent activity
Analyzing
Block #85,894,934
13 transactions · 11 stateful · 2026-07-06 03:23:37 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,894,934 · 13 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
2w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0217b2d…5aa3
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x024d2cfa…3a2d
0x34b655…2a6f
2 touches
0 conflicts
0x0d319aed…cac7
0x34b655…2a6f
2 touches
0 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
2 touches
0 conflicts
0x1e093e63…e4ef
0x34b655…2a6f
2 touches
0 conflicts
0x207cc41e…57c6
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 0xf0217b2dd8…f45aa3
Audit this contract →
← previous block·next block →recent activity