← previous blocknext block →recent activity
Analyzing
Block #86,305,030
15 transactions · 14 stateful · 2026-07-08 01:00:55 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,305,030 · 15 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
1w02w03w14w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe801f97b…5c2c
0xd32edf…ff58
3 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x658b88f5…2a09
0x065c9d…c394
2 touches
0 conflicts
0x8408e899…fed3
0x065c9d…c394
2 touches
0 conflicts
0x9940996e…56f4
0x065c9d…c394
2 touches
0 conflicts
0xbe64c38a…1b25
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