← previous blocknext block →recent activity
Analyzing
Block #101,816,529
14 transactions · 12 stateful · 2026-09-04 05:24:28 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,816,529 · 14 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
1w02w13w25w312w013w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49299fcf…c552
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9b8cfbd0…97ac
0x34b655…2a6f
4 touches
1 conflict
0xd001eaca…5a70
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4949d232…5502
0x34b655…2a6f
4 touches
1 conflict
0x463ff895…05c0
0x34b655…2a6f
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
10 conflicts on slot 0x49299fcf8b…f1c552
Audit this contract →
← previous block·next block →recent activity