← previous blocknext block →recent activity
Analyzing
Block #108,472,284
13 transactions · 11 stateful · 2026-09-27 13:03:45 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,472,284 · 13 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
2w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ae1f7fc…c539
0x065c9d…c394
2 touches
0 conflicts
0x35aced7b…efd3
0x065c9d…c394
2 touches
0 conflicts
0x4021bb59…d356
0x065c9d…c394
2 touches
0 conflicts
0x54a6c6c1…aaed
0x065c9d…c394
2 touches
0 conflicts
0x568b9843…6406
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