← previous blocknext block →recent activity
Analyzing
Block #106,906,731
23 transactions · 21 stateful · 2026-09-22 01:41:36 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,906,731 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w19w110w212w013w114w118w120w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd7940e5…d51a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x6ae47f75…7b45
0x34b655…2a6f
4 touches
1 conflict
0x7fc8f46e…0f75
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc44fc151…bd06
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 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
3 conflicts on slot 0xdd7940e542…ccd51a
Audit this contract →
← previous block·next block →recent activity