← previous blocknext block →recent activity
Analyzing
Block #106,301,271
14 transactions · 13 stateful · 2026-09-19 22:53:19 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,301,271 · 14 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
1w03w14w28w29w010w312w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x684d04c0…37c4
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd41f5136…97c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x14ea9ada…e628
0x34b655…2a6f
4 touches
1 conflict
0xeddf4d98…27f7
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9294
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
6 conflicts on slot 0x684d04c07a…7b37c4
Audit this contract →
← previous block·next block →recent activity