← previous blocknext block →recent activity
Analyzing
Block #106,423,104
18 transactions · 15 stateful · 2026-09-20 09:06:27 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,423,104 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w19w211w312w213w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa22eb76f…0f80
0x34b655…2a6f
8 touches
6 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
6 touches
3 conflicts
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x168f7615…a8dd
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
6 conflicts on slot 0xa22eb76f09…3d0f80
Audit this contract →
← previous block·next block →recent activity