← previous blocknext block →recent activity
Analyzing
Block #101,151,530
53 transactions · 39 stateful · 2026-09-01 21:38:55 UTC
Parallelism
59/100
Blocked
77%
Avg conflicts / tx
2.89
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #101,151,530 · 53 txs across 22 waves · depth 22
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w620w124w629w534w1038w644w1345w1448w1749w1850w1951w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xea02471d…1542
0x34b655…2a6f
18 touches
36 conflicts
0xf3d10975…0d07
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0019
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0029
0x1b6862…e19c
14 touches
21 conflicts
0x485d2778…aa5b
0x1b6862…e19c
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity