← previous blocknext block →recent activity
Analyzing
Block #105,931,751
22 transactions · 21 stateful · 2026-09-18 15:53:24 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,931,751 · 22 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
1w02w13w04w05w16w19w010w116w017w219w220w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xedbc2bb3…6b83
0x34b655…2a6f
6 touches
3 conflicts
0x16c911c2…e6f3
0x34b655…2a6f
6 touches
3 conflicts
0x24e14bd1…ebf2
0x34b655…2a6f
6 touches
3 conflicts
0xdb11940a…519b
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdbc6e634…e166
0x1b6862…e19c
4 touches
1 conflict
0x76f5a084…6117
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity