← previous blocknext block →recent activity
Analyzing
Block #99,991,587
41 transactions · 32 stateful · 2026-08-28 20:18:01 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,991,587 · 41 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w27w310w011w112w014w122w123w124w226w327w431w135w437w538w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xa605468c…1bfc
0x2b46c0…1669
8 touches
6 conflicts
0x06e40499…165e
0x2b46c0…1669
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
8 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0xf3331bf5…afb2
0xd32edf…ff58
7 touches
6 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity