← previous blocknext block →recent activity
Analyzing
Block #105,929,595
23 transactions · 23 stateful · 2026-09-18 15:42:33 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,929,595 · 23 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
1w02w03w15w07w08w19w211w112w013w115w117w218w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x302def9e…dd1d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x52f43fc9…66c6
0x34b655…2a6f
4 touches
1 conflict
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0x663d10cc…9cd9
0x34b655…2a6f
4 touches
1 conflict
0xa66499c2…9f47
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity