← previous blocknext block →recent activity
Analyzing
Block #106,301,505
19 transactions · 19 stateful · 2026-09-19 22:54:30 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,301,505 · 19 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
1w02w13w14w011w112w213w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x30ae635d…5e67
0x34b655…2a6f
8 touches
6 conflicts
0xf5d9f22d…e99f
0x34b655…2a6f
8 touches
6 conflicts
0xbbdfbf0e…2f1b
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xc1da8f73…484c
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity