← previous blocknext block →recent activity
Analyzing
Block #106,155,369
25 transactions · 22 stateful · 2026-09-19 10:38:58 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,155,369 · 25 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
2w03w14w15w26w07w112w013w116w217w319w320w423w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ed7cc0b…ee52
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x79b2e66a…64e7
0x34b655…2a6f
8 touches
6 conflicts
0x7c2ad520…3329
0x34b655…2a6f
8 touches
6 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
8 touches
6 conflicts
0xdbf974a4…b232
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0x0ed7cc0b4b…d2ee52
Audit this contract →
← previous block·next block →recent activity