← previous blocknext block →recent activity
Analyzing
Block #106,184,800
38 transactions · 36 stateful · 2026-09-19 13:07:05 UTC
Parallelism
66/100
Blocked
64%
Avg conflicts / tx
3.11
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,184,800 · 38 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w112w213w214w315w416w517w619w520w621w722w823w924w1025w1126w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27f401e8…a4fe
0x34b655…2a6f
22 touches
55 conflicts
0xee64690f…0799
0x34b655…2a6f
20 touches
45 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
14 touches
21 conflicts
0x4bcbd0e7…5e26
0x34b655…2a6f
13 touches
21 conflicts
0x80398c66…f3cc
0x34b655…2a6f
12 touches
15 conflicts
0x4786839b…c29a
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x27f401e818…6aa4fe
Audit this contract →
← previous block·next block →recent activity