← previous blocknext block →recent activity
Analyzing
Block #106,380,365
9 transactions · 9 stateful · 2026-09-20 05:31:22 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,380,365 · 9 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
2w03w14w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc3207c1…fad6
0x34b655…2a6f
4 touches
1 conflict
0xce06a0f7…efef
0x34b655…2a6f
4 touches
1 conflict
0x22db2187…cb6b
0x34b655…2a6f
4 touches
1 conflict
0x2ecf2f58…42d9
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x1b5b0c97…d824
0x34b655…2a6f
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 0xcc3207c136…affad6
Audit this contract →
← previous block·next block →recent activity