← previous blocknext block →recent activity
Analyzing
Block #86,319,400
33 transactions · 31 stateful · 2026-07-08 02:37:00 UTC
Parallelism
85/100
Blocked
19%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,319,400 · 33 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
1w02w13w217w018w320w026w428w329w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
8 touches
6 conflicts
0xda8eaa80…b086
0x065c9d…c394
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
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
6 conflicts on slot 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity