← previous blocknext block →recent activity
Analyzing
Block #108,605,563
53 transactions · 49 stateful · 2026-09-28 00:14:52 UTC
Parallelism
89/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,605,563 · 53 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w08w19w010w111w213w014w115w219w120w221w322w427w128w334w235w336w437w545w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0xd38669f7…e913
0x065c9d…c394
5 touches
3 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity