← previous blocknext block →recent activity
Analyzing
Block #106,467,984
15 transactions · 14 stateful · 2026-09-20 12:52:22 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,467,984 · 15 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
1w02w13w04w15w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b17b0ae…fccf
0x34b655…2a6f
4 touches
1 conflict
0x8b52b75c…8a0d
0xa6afd3…d132
4 touches
1 conflict
0x5ef326ed…69dc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x60a31abc…bb36
0x34b655…2a6f
4 touches
1 conflict
0x4265984a…a7d2
0x34b655…2a6f
4 touches
1 conflict
0x64b81b9f…3c48
0xd32edf…ff58
3 touches
1 conflict
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