← previous blocknext block →recent activity
Analyzing
Block #105,931,465
23 transactions · 19 stateful · 2026-09-18 15:51:58 UTC
Parallelism
52/100
Blocked
63%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,931,465 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w511w613w714w715w816w917w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3abeb65c…dc1c
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x375b6201…9c1e
0x34b655…2a6f
10 touches
10 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xd8d828a7…b649
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x05d9b05f…d22c
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0x3abeb65c0a…5adc1c
Audit this contract →
← previous block·next block →recent activity