← previous blocknext block →recent activity
Analyzing
Block #106,282,194
18 transactions · 18 stateful · 2026-09-19 21:17:20 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,282,194 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w010w011w112w213w314w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10dd9c29…2746
0x6f6493…b480
10 touches
10 conflicts
0x10dd9c29…274a
0x6f6493…b480
10 touches
10 conflicts
0x14254afe…8bc5
0x6f6493…b480
10 touches
10 conflicts
0x30a8edc0…049e
0x6f6493…b480
10 touches
10 conflicts
0x317e21e9…b6c5
0x6f6493…b480
10 touches
10 conflicts
0x353571bf…052d
0x6f6493…b480
10 touches
10 conflicts
0x37a203d4…c011
0x6f6493…b480
10 touches
10 conflicts
0x3b806b46…770a
0x6f6493…b480
10 touches
10 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
10 conflicts on slot 0x10dd9c29eb…892746
Audit this contract →
← previous block·next block →recent activity