← previous blocknext block →recent activity
Analyzing
Block #106,434,841
7 transactions · 6 stateful · 2026-09-20 10:05:32 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,434,841 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b17b0ae…fccf
0x34b655…2a6f
4 touches
1 conflict
0x821c3e00…3226
0x34b655…2a6f
4 touches
1 conflict
0xfc05bc16…2e8c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0xac2a0273…721b
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
2 touches
0 conflicts
0xee7b2000…d0ad
0x34b655…2a6f
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