← previous blocknext block →recent activity
Analyzing
Block #105,470,155
51 transactions · 35 stateful · 2026-09-17 01:07:51 UTC
Parallelism
84/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,470,155 · 51 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w010w013w114w215w116w118w320w028w138w439w542w443w644w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0xd35bb5ac…3586
0x065c9d…c394
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xa4f80979…4d71
0x065c9d…c394
10 touches
10 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 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