← previous blocknext block →recent activity
Analyzing
Block #86,355,818
16 transactions · 14 stateful · 2026-07-08 06:40:09 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,355,818 · 16 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
1w02w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x105cfb90…c9b9
0x065c9d…c394
2 touches
0 conflicts
0x11431a59…698f
0x065c9d…c394
2 touches
0 conflicts
0x50c4f92e…aeb3
0x065c9d…c394
2 touches
0 conflicts
0x9952457b…d78f
0x065c9d…c394
2 touches
0 conflicts
0xbc50d5a3…a248
0x065c9d…c394
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity