← previous blocknext block →recent activity
Analyzing
Block #106,959,213
19 transactions · 18 stateful · 2026-09-22 06:05:47 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,959,213 · 19 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
1w02w110w211w312w015w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d81790c…b9f7
0x34b655…2a6f
8 touches
6 conflicts
0xe101d25e…377a
0x34b655…2a6f
6 touches
3 conflicts
0x6ae47f75…7b45
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc6785f04…7c11
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc953c572…34b1
0x34b655…2a6f
4 touches
1 conflict
0x24b6091e…d294
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 0x1d81790c4e…7cb9f7
Audit this contract →
← previous block·next block →recent activity