← previous blocknext block →recent activity
Analyzing
Block #106,577,762
21 transactions · 19 stateful · 2026-09-20 22:04:52 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,577,762 · 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
1w02w03w14w27w113w314w215w316w417w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad401fc6…8648
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x5ce28434…11ee
0x34b655…2a6f
4 touches
1 conflict
0x7a903e28…f9ef
0x34b655…2a6f
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
15 conflicts on slot 0xad401fc6dc…ea8648
Audit this contract →
← previous block·next block →recent activity