← previous blocknext block →recent activity
Analyzing
Block #106,016,116
16 transactions · 16 stateful · 2026-09-18 22:58:10 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,016,116 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w17w08w19w210w311w412w513w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b9ee0be…9e03
0x6f6493…b480
14 touches
21 conflicts
0xfedd2841…3cf3
0x6f6493…b480
14 touches
21 conflicts
0xcaa1f5e4…9374
0x6f6493…b480
14 touches
21 conflicts
0x14263f4a…39e5
0x6f6493…b480
14 touches
21 conflicts
0x32fc5216…c43e
0x6f6493…b480
14 touches
21 conflicts
0x37180465…a007
0x6f6493…b480
14 touches
21 conflicts
0x608f2744…804d
0x6f6493…b480
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0x9b9ee0be40…609e03
Audit this contract →
← previous block·next block →recent activity