← previous blocknext block →recent activity
Analyzing
Block #106,189,409
29 transactions · 27 stateful · 2026-09-19 13:30:17 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,189,409 · 29 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
1w02w03w14w15w27w08w09w111w012w114w216w017w118w020w121w222w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9baf24c…c1fe
0x34b655…2a6f
10 touches
10 conflicts
0xfe5f5aab…21d7
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x4607e809…cc62
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
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 0xf9baf24cdf…38c1fe
Audit this contract →
← previous block·next block →recent activity