← previous blocknext block →recent activity
Analyzing
Block #106,004,354
19 transactions · 16 stateful · 2026-09-18 21:58:59 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,004,354 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w210w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb039cff5…c9f4
0x065c9d…c394
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x4456f3d0…c78f
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
2 touches
0 conflicts
0x00000000…0001
0x2d82ac…5fd8
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
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
6 conflicts on slot 0xb039cff507…44c9f4
Audit this contract →
← previous block·next block →recent activity