← previous blocknext block →recent activity
Analyzing
Block #100,917,789
29 transactions · 22 stateful · 2026-09-01 02:02:40 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,917,789 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w29w010w111w212w317w123w324w425w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xd43f9831…fac1
0x065c9d…c394
5 touches
3 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0xf80284a5…4bed
0x065c9d…c394
4 touches
1 conflict
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity