← previous blocknext block →recent activity
Analyzing
Block #101,322,607
19 transactions · 17 stateful · 2026-09-02 11:59:37 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,322,607 · 19 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
2w05w06w18w010w112w113w214w317w018w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe8f5e33f…719c
0x34b655…2a6f
6 touches
3 conflicts
0x1653f4fe…be5f
0x34b655…2a6f
6 touches
3 conflicts
0x12e7c471…901c
0x34b655…2a6f
6 touches
3 conflicts
0x5d5884de…a04e
0x34b655…2a6f
4 touches
1 conflict
0x60538f8e…6ed6
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity