← previous blocknext block →recent activity
Analyzing
Block #101,304,234
18 transactions · 15 stateful · 2026-09-02 10:27:10 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,304,234 · 18 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
1w05w06w17w112w215w016w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c2b0f0e…4933
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x16d77246…bac5
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x556beb43…e627
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0xd6a9c74e…d97d
0x34b655…2a6f
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 0x7c2b0f0e0c…a44933
Audit this contract →
← previous block·next block →recent activity