← previous blocknext block →recent activity
Analyzing
Block #86,349,047
21 transactions · 17 stateful · 2026-07-08 05:54:56 UTC
Parallelism
90/100
Blocked
6%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,349,047 · 21 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
1w09w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb0337f42…c058
0x065c9d…c394
3 touches
1 conflict
0x07cf2c2d…fe93
0x065c9d…c394
3 touches
1 conflict
0x0661698f…8cc0
0x065c9d…c394
3 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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