← previous blocknext block →recent activity
Analyzing
Block #101,491,270
17 transactions · 16 stateful · 2026-09-03 02:08:19 UTC
Parallelism
47/100
Blocked
50%
Avg conflicts / tx
1.12
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,491,270 · 17 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
1w02w13w24w05w36w47w511w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6823c28e…594c
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xf7772b49…fc12
0x34b655…2a6f
8 touches
6 conflicts
0x9c088939…ddd7
0x34b655…2a6f
8 touches
6 conflicts
0x4778019e…cac4
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x58c745f6…fe5d
0x34b655…2a6f
6 touches
3 conflicts
0x6c7c1a4b…5751
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 0x6823c28eb2…d0594c
Audit this contract →
← previous block·next block →recent activity