← previous blocknext block →recent activity
Analyzing
Block #101,301,334
7 transactions · 7 stateful · 2026-09-02 10:12:34 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,301,334 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e07769b…a191
0x34b655…2a6f
4 touches
1 conflict
0x88e92ec7…696d
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x04c70b12…1178
0x34b655…2a6f
4 touches
1 conflict
0x567151c4…8429
0x34b655…2a6f
3 touches
1 conflict
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x21b04722…0000
0x447d2e…e9f5
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 0x5e07769be2…39a191
Audit this contract →
← previous block·next block →recent activity