← previous blocknext block →recent activity
Analyzing
Block #85,780,781
20 transactions · 18 stateful · 2026-07-05 14:43:10 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,780,781 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w18w09w110w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ad89ba…cf83
0x0a917f…7777
16 touches
28 conflicts
0x00000000…0000
0x431fed…d150
16 touches
28 conflicts
0x00000000…0002
0x431fed…d150
16 touches
28 conflicts
0x00000000…0003
0x431fed…d150
16 touches
28 conflicts
0x1ccfa324…0b93
0x0a917f…7777
16 touches
28 conflicts
0xa472d565…9fe4
0x3bd359…433a
16 touches
28 conflicts
0xe6f2ae57…2026
0x3bd359…433a
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
28 conflicts on slot 0x44ad89ba62…49cf83
Audit this contract →
← previous block·next block →recent activity