← previous blocknext block →recent activity
Analyzing
Block #106,389,614
17 transactions · 16 stateful · 2026-09-20 06:17:55 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,389,614 · 17 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
1w05w16w27w310w011w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06103b27…dc55
0x6f6493…b480
12 touches
15 conflicts
0x06103b27…dc59
0x6f6493…b480
12 touches
15 conflicts
0x0e6c8c49…1083
0x6f6493…b480
12 touches
15 conflicts
0x20ef0dc3…0ba3
0x6f6493…b480
12 touches
15 conflicts
0x3347c485…6951
0x6f6493…b480
12 touches
15 conflicts
0x3ce59502…46ca
0x6f6493…b480
12 touches
15 conflicts
0x40007e43…4285
0x6f6493…b480
12 touches
15 conflicts
0x43b4d903…388b
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 0x06103b2772…5fdc55
Audit this contract →
← previous block·next block →recent activity