← previous blocknext block →recent activity
Analyzing
Block #96,132,477
15 transactions · 14 stateful · 2026-08-15 06:31:07 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,132,477 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x8f480c9a…467c
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x4d1e3e31…edf8
0x3bd359…433a
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 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity