← previous blocknext block →recent activity
Analyzing
Block #101,019,644
21 transactions · 21 stateful · 2026-09-01 10:35:06 UTC
Parallelism
57/100
Blocked
52%
Avg conflicts / tx
1.62
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,019,644 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w08w19w211w314w215w416w317w518w620w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40f0cbff…df7c
0x34b655…2a6f
10 touches
10 conflicts
0x97e4c862…4419
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfd30ecce…02c0
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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
10 conflicts on slot 0x40f0cbff72…3adf7c
Audit this contract →
← previous block·next block →recent activity