← previous blocknext block →recent activity
Analyzing
Block #105,470,679
20 transactions · 20 stateful · 2026-09-17 01:10:29 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,470,679 · 20 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
1w02w13w24w010w011w112w213w314w415w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x025cdb2f…16e1
0x6f6493…b480
12 touches
15 conflicts
0x0f7f20af…510d
0x6f6493…b480
12 touches
15 conflicts
0x148d492b…a5ca
0x6f6493…b480
12 touches
15 conflicts
0x16491c66…4d2b
0x6f6493…b480
12 touches
15 conflicts
0x28e53f99…e387
0x6f6493…b480
12 touches
15 conflicts
0x2bb6e2e0…8c7a
0x6f6493…b480
12 touches
15 conflicts
0x364dac6b…e5c1
0x6f6493…b480
12 touches
15 conflicts
0x3d134358…56cb
0x6f6493…b480
12 touches
15 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: 0x6f6493e3…08b480
15 conflicts on slot 0x025cdb2f21…a616e1
Audit this contract →
← previous block·next block →recent activity