← previous blocknext block →recent activity
Analyzing
Block #106,403,378
19 transactions · 19 stateful · 2026-09-20 07:27:10 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,403,378 · 19 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
1w02w13w210w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10e2f4e5…90d5
0x6f6493…b480
12 touches
15 conflicts
0x16258db2…c590
0x6f6493…b480
12 touches
15 conflicts
0x166fab8c…2b4c
0x6f6493…b480
12 touches
15 conflicts
0x282cbd3b…eea0
0x6f6493…b480
12 touches
15 conflicts
0x2dc6b641…fa71
0x6f6493…b480
12 touches
15 conflicts
0x429cde60…43f4
0x6f6493…b480
12 touches
15 conflicts
0x44f4b396…9d5d
0x6f6493…b480
12 touches
15 conflicts
0x4ff90412…3f09
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 0x10e2f4e578…1c90d5
Audit this contract →
← previous block·next block →recent activity