← previous blocknext block →recent activity
Analyzing
Block #99,211,913
14 transactions · 9 stateful · 2026-08-26 02:39:30 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,211,913 · 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
2w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedcfab31…6308
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf5ef69f1…65c7
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001b
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 0xedcfab31ab…2c6308
Audit this contract →
← previous block·next block →recent activity