← previous blocknext block →recent activity
Analyzing
Block #86,047,344
36 transactions · 26 stateful · 2026-07-06 20:20:58 UTC
Parallelism
86/100
Blocked
46%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,047,344 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w07w18w29w110w214w016w121w323w226w128w432w033w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xee4ad79f…3c32
0xd32edf…ff58
5 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
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
3 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity