← previous blocknext block →recent activity
Analyzing
Block #101,500,382
10 transactions · 10 stateful · 2026-09-03 02:54:10 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,500,382 · 10 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
2w03w14w25w36w47w08w19w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb70f92cf…da8b
0x34b655…2a6f
8 touches
6 conflicts
0x26c599c1…706c
0x34b655…2a6f
6 touches
3 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
6 touches
3 conflicts
0x375a37a1…ac05
0x34b655…2a6f
6 touches
3 conflicts
0x4b024b98…8f37
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x664f4148…0cfb
0x34b655…2a6f
6 touches
3 conflicts
0x67043b0b…97d7
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 0xb70f92cf9e…55da8b
Audit this contract →
← previous block·next block →recent activity