← previous blocknext block →recent activity
Analyzing
Block #105,869,359
30 transactions · 28 stateful · 2026-09-18 10:38:30 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,869,359 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w214w115w216w321w222w323w424w525w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x6771eae2…7014
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x0f94ee4c…1897
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x23529e13…6f25
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 0x80398c66c8…7ef3cc
Audit this contract →
← previous block·next block →recent activity