← previous blocknext block →recent activity
Analyzing
Block #101,151,042
15 transactions · 12 stateful · 2026-09-01 21:36:28 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,151,042 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w08w211w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad563cd8…d60d
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x81ceb686…4df3
0x34b655…2a6f
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 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
1 conflict on slot 0xad563cd8ea…8ed60d
Audit this contract →
← previous block·next block →recent activity