← previous blocknext block →recent activity
Analyzing
Block #85,458,434
12 transactions · 12 stateful · 2026-07-04 02:55:47 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,458,434 · 12 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
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbf607f62…a643
0x065c9d…c394
4 touches
1 conflict
0x1243f6ba…6fbf
0x065c9d…c394
2 touches
0 conflicts
0xbba4c0c4…241a
0x065c9d…c394
2 touches
0 conflicts
0xe588f517…af00
0x065c9d…c394
2 touches
0 conflicts
0xebdb64a6…7758
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity