← previous blocknext block →recent activity
Analyzing
Block #86,507,091
15 transactions · 12 stateful · 2026-07-08 23:31:03 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,507,091 · 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x03367510…9b91
0x065c9d…c394
2 touches
0 conflicts
0x0e84d0ad…47d2
0x065c9d…c394
2 touches
0 conflicts
0x35a578a7…a131
0x065c9d…c394
2 touches
0 conflicts
0xcba3e575…ba89
0x065c9d…c394
2 touches
0 conflicts
0xd35bb5ac…3586
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: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity