← previous blocknext block →recent activity
Analyzing
Block #105,870,141
21 transactions · 20 stateful · 2026-09-18 10:42:26 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,870,141 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w18w09w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dccd2a9…2790
0x34b655…2a6f
10 touches
10 conflicts
0xc51d3dfe…4a25
0x34b655…2a6f
10 touches
10 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…4734
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0x9dccd2a98b…6d2790
Audit this contract →
← previous block·next block →recent activity