← previous blocknext block →recent activity
Analyzing
Block #100,627,435
22 transactions · 18 stateful · 2026-08-31 01:41:42 UTC
Parallelism
91/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,627,435 · 22 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
5w06w18w09w011w112w013w115w016w117w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed3e0ae5…d0c2
0x065c9d…c394
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0xed3e0ae5d2…6ad0c2
Audit this contract →
← previous block·next block →recent activity