← previous blocknext block →recent activity
Analyzing
Block #100,026,713
15 transactions · 13 stateful · 2026-08-28 23:14:51 UTC
Parallelism
80/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,026,713 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xe00b52f1…04ca
0x065c9d…c394
3 touches
1 conflict
0x17fa6222…9bd6
0x065c9d…c394
3 touches
1 conflict
0x733a6e8d…ef48
0x065c9d…c394
3 touches
1 conflict
0x9b547cf0…2807
0x065c9d…c394
3 touches
1 conflict
0x13807d54…85db
0x34b655…2a6f
2 touches
0 conflicts
0x16d77246…bac5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity