← previous blocknext block →recent activity
Analyzing
Block #106,473,677
27 transactions · 20 stateful · 2026-09-20 13:21:01 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,473,677 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w07w010w116w017w118w219w322w123w124w125w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23592ab4…9ba8
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0xd1dad4ed…292c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x732ce5dc…9452
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
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
10 conflicts on slot 0x23592ab41f…e39ba8
Audit this contract →
← previous block·next block →recent activity