← previous blocknext block →recent activity
Analyzing
Block #106,200,427
36 transactions · 31 stateful · 2026-09-19 14:25:44 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,200,427 · 36 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w08w113w219w220w322w423w124w531w632w733w834w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0xa800bb04…1d40
0x34b655…2a6f
7 touches
6 conflicts
0x7674d852…fcfb
0x34b655…2a6f
6 touches
3 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity