← previous blocknext block →recent activity
Analyzing
Block #106,430,666
20 transactions · 18 stateful · 2026-09-20 09:44:30 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,430,666 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w09w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
12 touches
15 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x51d607f1…6458
0x34b655…2a6f
8 touches
6 conflicts
0x40c584a0…3f07
0x34b655…2a6f
8 touches
6 conflicts
0x2029b74e…c206
0x34b655…2a6f
8 touches
6 conflicts
0x4b8f9060…8773
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x2511f10d…9773
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
15 conflicts on slot 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity