← previous blocknext block →recent activity
Analyzing
Block #101,309,281
29 transactions · 25 stateful · 2026-09-02 10:52:34 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,309,281 · 29 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
1w05w06w17w08w010w112w013w122w223w324w125w227w028w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213b816c…a5e0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x166cd7f7…2b93
0x34b655…2a6f
4 touches
1 conflict
0x2d3ce3bf…073a
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 0x213b816cc7…d4a5e0
Audit this contract →
← previous block·next block →recent activity