← previous blocknext block →recent activity
Analyzing
Block #106,197,872
19 transactions · 16 stateful · 2026-09-19 14:12:52 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,197,872 · 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
1w02w13w011w112w214w215w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x9167c873…748f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
1 conflict on slot 0x4d5053d1f9…c83b7d
Audit this contract →
← previous block·next block →recent activity