← previous blocknext block →recent activity
Analyzing
Block #100,028,086
14 transactions · 13 stateful · 2026-08-28 23:21:46 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,028,086 · 14 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
1w02w15w28w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7518f12…13e5
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x9ba7d0c8…ec52
0xee8c0e…1242
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x354d92…66fb
4 touches
1 conflict
0x00000000…0001
0x354d92…66fb
4 touches
1 conflict
0xe90b7bce…c2e0
0x354d92…66fb
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0xf7518f1299…dc13e5
Audit this contract →
← previous block·next block →recent activity