← previous blocknext block →recent activity
Analyzing
Block #101,815,907
40 transactions · 21 stateful · 2026-09-04 05:21:20 UTC
Parallelism
90/100
Blocked
38%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,815,907 · 40 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w116w017w018w120w021w128w029w231w132w138w239w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0xa7006b15…16ff
0xd32edf…ff58
5 touches
3 conflicts
0x34dad526…5f98
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
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
3 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity