← previous blocknext block →recent activity
Analyzing
Block #105,759,405
25 transactions · 23 stateful · 2026-09-18 01:23:40 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,759,405 · 25 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
1w02w13w14w25w37w08w19w010w113w314w418w219w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bbdf7d0…04c4
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x0e73da68…dcd5
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
8 touches
6 conflicts
0xb3d671ff…a53b
0x34b655…2a6f
8 touches
6 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
8 touches
6 conflicts
0xf48fa71e…bb52
0x34b655…2a6f
8 touches
6 conflicts
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 0x3bbdf7d016…9804c4
Audit this contract →
← previous block·next block →recent activity