← previous blocknext block →recent activity
Analyzing
Block #99,155,241
7 transactions · 7 stateful · 2026-08-25 21:54:24 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,155,241 · 7 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
1w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1c25f832…2621
0x065c9d…c394
2 touches
0 conflicts
0x3ff9c228…2714
0x065c9d…c394
2 touches
0 conflicts
0x5fddea82…23ca
0x065c9d…c394
2 touches
0 conflicts
0x9864d0ae…3099
0x065c9d…c394
2 touches
0 conflicts
0xbfa58667…d1e2
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