← previous blocknext block →recent activity
Analyzing
Block #106,009,569
16 transactions · 15 stateful · 2026-09-18 22:25:14 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,009,569 · 16 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
1w02w03w18w110w011w112w213w314w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fb24af0…5f57
0x6f6493…b480
10 touches
10 conflicts
0x281fdc04…7013
0x6f6493…b480
10 touches
10 conflicts
0x3002edd8…35db
0x6f6493…b480
10 touches
10 conflicts
0x38341598…e602
0x6f6493…b480
10 touches
10 conflicts
0x3ccfd5d4…32ed
0x6f6493…b480
10 touches
10 conflicts
0x3d546bec…dbe9
0x6f6493…b480
10 touches
10 conflicts
0x3e2b7bcf…b805
0x6f6493…b480
10 touches
10 conflicts
0x45013623…fb7a
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 0x0fb24af0c4…295f57
Audit this contract →
← previous block·next block →recent activity