← previous blocknext block →recent activity
Analyzing
Block #106,100,605
24 transactions · 22 stateful · 2026-09-19 06:03:22 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,100,605 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w18w112w213w014w115w218w320w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x047eed46…4d4f
0x6f6493…b480
6 touches
3 conflicts
0x086042c4…d1fe
0x6f6493…b480
6 touches
3 conflicts
0x1395ac51…99b4
0x6f6493…b480
6 touches
3 conflicts
0x1a0c370c…6732
0x6f6493…b480
6 touches
3 conflicts
0x1a8cf04d…8753
0x6f6493…b480
6 touches
3 conflicts
0x212bddcb…fdff
0x6f6493…b480
6 touches
3 conflicts
0x347f6742…9e77
0x6f6493…b480
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity