← previous blocknext block →recent activity
Analyzing
Block #100,095,400
17 transactions · 14 stateful · 2026-08-29 05:00:37 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,095,400 · 17 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
1w02w04w111w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd26e1184…50b7
0x065c9d…c394
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0xb6e3bf47…74d0
0x065c9d…c394
3 touches
1 conflict
0xebc2e0d7…958e
0x3bd359…433a
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
3 conflicts on slot 0xd26e1184b3…b250b7
Audit this contract →
← previous block·next block →recent activity