← previous blocknext block →recent activity
Analyzing
Block #106,252,476
21 transactions · 21 stateful · 2026-09-19 18:47:47 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
1.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,252,476 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w18w29w113w214w315w416w517w619w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e6302c8…64f5
0x34b655…2a6f
10 touches
10 conflicts
0x6b267bdf…b173
0x34b655…2a6f
10 touches
10 conflicts
0x03537d13…069b
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
8 touches
6 conflicts
0xd3b627bf…69d4
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x46372257…6f65
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x3e6302c867…b164f5
Audit this contract →
← previous block·next block →recent activity