← previous blocknext block →recent activity
Analyzing
Block #99,090,018
12 transactions · 12 stateful · 2026-08-25 16:26:06 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,090,018 · 12 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
1w02w06w07w19w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe8cbe85…9c51
0x065c9d…c394
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xf984d8ab…6e4f
0x34b655…2a6f
4 touches
1 conflict
0xb81c8b5b…fe53
0x065c9d…c394
2 touches
0 conflicts
0xbf79bbc8…3c04
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0xbe8cbe852d…979c51
Audit this contract →
← previous block·next block →recent activity