← previous blocknext block →recent activity
Analyzing
Block #85,856,106
33 transactions · 26 stateful · 2026-07-05 23:05:05 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,856,106 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w09w010w311w012w113w114w216w017w118w227w128w230w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ccfa324…0b93
0x0a917f…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0x0a917f…7777
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xe6f2ae57…2026
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x431fed…d150
6 touches
3 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: 0x0a917fcc…9d7777
3 conflicts on slot 0x1ccfa32498…500b93
Audit this contract →
← previous block·next block →recent activity