← previous blocknext block →recent activity
Analyzing
Block #106,273,356
19 transactions · 18 stateful · 2026-09-19 20:32:51 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,273,356 · 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
4w05w18w010w011w112w013w114w215w316w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1210d62a…116c
0x6f6493…b480
8 touches
6 conflicts
0x1e0ad5ff…fab7
0x6f6493…b480
8 touches
6 conflicts
0x1f4a75e3…14a0
0x6f6493…b480
8 touches
6 conflicts
0x1f4a75e3…14a4
0x6f6493…b480
8 touches
6 conflicts
0x24b77969…9232
0x6f6493…b480
8 touches
6 conflicts
0x3332a07f…a0f2
0x6f6493…b480
8 touches
6 conflicts
0x40c0fa31…f548
0x6f6493…b480
8 touches
6 conflicts
0x41bc1877…d0df
0x6f6493…b480
8 touches
6 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
6 conflicts on slot 0x1210d62a0c…6d116c
Audit this contract →
← previous block·next block →recent activity