← previous blocknext block →recent activity
Analyzing
Block #99,354,866
14 transactions · 13 stateful · 2026-08-26 14:38:47 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,354,866 · 14 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
5w010w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec93cff…9db9
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa6dbb1a1…da8f
0x065c9d…c394
3 touches
1 conflict
0xdf6ae4d4…881b
0x065c9d…c394
3 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
0xc08384da…ecb7
0x34b655…2a6f
2 touches
0 conflicts
0xd4893967…d7f3
0x34b655…2a6f
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 0x4ec93cff76…ee9db9
Audit this contract →
← previous block·next block →recent activity