← previous blocknext block →recent activity
Analyzing
Block #108,419,496
14 transactions · 11 stateful · 2026-09-27 08:38:03 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,419,496 · 14 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
5w07w19w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe88813ec…bd64
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6ea8fa8d…3dd7
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xda22da74…4556
0xd32edf…ff58
3 touches
1 conflict
0x2f9136e2…5522
0x065c9d…c394
3 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 0xe88813ec2a…e0bd64
Audit this contract →
← previous block·next block →recent activity