← previous blocknext block →recent activity
Analyzing
Block #106,403,925
14 transactions · 14 stateful · 2026-09-20 07:29:55 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,403,925 · 14 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
2w03w14w15w28w29w310w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a55a9d1…e7ce
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x5364a0e7…41fc
0x34b655…2a6f
8 touches
6 conflicts
0xfbdeb88b…e19a
0x34b655…2a6f
6 touches
3 conflicts
0x611a16a4…f6b1
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x5a55a9d1da…40e7ce
Audit this contract →
← previous block·next block →recent activity