← previous blocknext block →recent activity
Analyzing
Block #106,802,108
20 transactions · 19 stateful · 2026-09-21 16:55:00 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,802,108 · 20 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
1w02w03w14w07w08w19w211w113w214w215w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9edb7ad7…8d56
0x34b655…2a6f
12 touches
15 conflicts
0xc99d677b…2040
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0xdd2800d9…7d27
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
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 0x9edb7ad7f2…288d56
Audit this contract →
← previous block·next block →recent activity