← previous blocknext block →recent activity
Analyzing
Block #106,380,344
16 transactions · 15 stateful · 2026-09-20 05:31:15 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,380,344 · 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
4w05w17w08w09w110w211w312w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01b61ab1…c053
0x6f6493…b480
10 touches
10 conflicts
0x0465e2e2…cd43
0x6f6493…b480
10 touches
10 conflicts
0x084b6cd2…b55c
0x6f6493…b480
10 touches
10 conflicts
0x0e720ff4…7570
0x6f6493…b480
10 touches
10 conflicts
0x0e720ff4…7574
0x6f6493…b480
10 touches
10 conflicts
0x1a55e9b2…257d
0x6f6493…b480
10 touches
10 conflicts
0x1bc5363b…8093
0x6f6493…b480
10 touches
10 conflicts
0x1c0c8e63…cbee
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 0x01b61ab137…e5c053
Audit this contract →
← previous block·next block →recent activity