← previous blocknext block →recent activity
Analyzing
Block #101,925,571
22 transactions · 16 stateful · 2026-09-04 14:34:22 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,925,571 · 22 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
5w06w17w28w39w010w113w120w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d0c4a4…add3
0x34b655…2a6f
8 touches
6 conflicts
0xf4c98c5b…706a
0x34b655…2a6f
8 touches
6 conflicts
0x2f17174f…68b4
0x34b655…2a6f
6 touches
3 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
6 touches
3 conflicts
0x41c56387…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0x4b024b98…8f37
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x26c599c1…706c
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 0x66d0c4a46b…adadd3
Audit this contract →
← previous block·next block →recent activity