← previous blocknext block →recent activity
Analyzing
Block #100,853,905
23 transactions · 17 stateful · 2026-08-31 20:41:20 UTC
Parallelism
91/100
Blocked
6%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,853,905 · 23 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x9dc6f38d…5024
0x065c9d…c394
2 touches
0 conflicts
0xd02993f3…3d83
0x065c9d…c394
2 touches
0 conflicts
0xf2636932…a43f
0x065c9d…c394
2 touches
0 conflicts
0xf576ce27…7364
0x065c9d…c394
2 touches
0 conflicts
0xf9458be7…96c0
0x065c9d…c394
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