← previous blocknext block →recent activity
Analyzing
Block #106,030,699
13 transactions · 12 stateful · 2026-09-19 00:11:34 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,030,699 · 13 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
1w05w18w010w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd91f9aca…3735
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb6e0b4cf…e3a5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x98a1bad6…5130
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xd91f9acaaf…143735
Audit this contract →
← previous block·next block →recent activity