← previous blocknext block →recent activity
Analyzing
Block #106,429,161
18 transactions · 15 stateful · 2026-09-20 09:36:55 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,429,161 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w18w09w112w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b17b0ae…fccf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xba33378a…f1df
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x3194fbf2…6bcf
0x34b655…2a6f
4 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
2 touches
0 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
1 conflict on slot 0x5b17b0ae3f…05fccf
Audit this contract →
← previous block·next block →recent activity