← previous blocknext block →recent activity
Analyzing
Block #99,976,119
38 transactions · 28 stateful · 2026-08-28 19:00:05 UTC
Parallelism
84/100
Blocked
54%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,976,119 · 38 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
3w04w05w17w211w116w318w019w123w324w026w127w228w229w030w131w232w335w336w437w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5f77d607…2c84
0x065c9d…c394
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity