← previous blocknext block →recent activity
Analyzing
Block #101,670,903
18 transactions · 15 stateful · 2026-09-03 17:12:00 UTC
Parallelism
61/100
Blocked
60%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,670,903 · 18 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
1w02w03w14w06w17w29w210w311w413w314w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x885efce3…7496
0x34b655…2a6f
6 touches
3 conflicts
0x58edd443…786c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x64b7d292…67c9
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x110a3804…f842
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 0x885efce3b0…367496
Audit this contract →
← previous block·next block →recent activity