← previous blocknext block →recent activity
Analyzing
Block #100,878,462
18 transactions · 16 stateful · 2026-08-31 22:44:51 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,878,462 · 18 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
3w04w15w210w311w412w513w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5c270ed…c835
0x065c9d…c394
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0xcaa41b23…275a
0x065c9d…c394
4 touches
1 conflict
0x00000000…002c
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
6 conflicts on slot 0xc5c270ed1c…f4c835
Audit this contract →
← previous block·next block →recent activity