← previous blocknext block →recent activity
Analyzing
Block #88,087,194
17 transactions · 16 stateful · 2026-07-16 07:39:08 UTC
Parallelism
82/100
Blocked
19%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,087,194 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w012w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x5777bd87…71bd
0x34b655…2a6f
4 touches
1 conflict
0x9be6705f…ec50
0x34b655…2a6f
4 touches
1 conflict
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0x36385a2d…35f8
0x34b655…2a6f
4 touches
1 conflict
0xb14d2998…2814
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity