← previous blocknext block →recent activity
Analyzing
Block #100,125,013
24 transactions · 23 stateful · 2026-08-29 07:29:44 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,125,013 · 24 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
1w08w09w111w112w014w115w019w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc50fa3…11dd
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xbd3735d7…c973
0x34b655…2a6f
4 touches
1 conflict
0xc20bb30f…7331
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xded7831c…3c4a
0x34b655…2a6f
4 touches
1 conflict
0xf61165ef…adb9
0x34b655…2a6f
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
1 conflict on slot 0x5cc50fa3bb…d911dd
Audit this contract →
← previous block·next block →recent activity