← previous blocknext block →recent activity
Analyzing
Block #100,926,152
11 transactions · 11 stateful · 2026-09-01 02:44:44 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,926,152 · 11 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7a757ae8…9a26
0x065c9d…c394
3 touches
1 conflict
0xc0a4237a…10d1
0x065c9d…c394
3 touches
1 conflict
0x005622bd…c320
0x065c9d…c394
2 touches
0 conflicts
0x52438f9f…0f1c
0x065c9d…c394
2 touches
0 conflicts
0x80cc11b3…0774
0x065c9d…c394
2 touches
0 conflicts
0x80cc11b3…0775
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
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