← previous blocknext block →recent activity
Analyzing
Block #101,656,567
16 transactions · 14 stateful · 2026-09-03 15:59:53 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,656,567 · 16 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
1w02w13w04w15w26w29w310w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc52785b9…08f8
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
6 touches
3 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
6 touches
3 conflicts
0xfd713bab…a651
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x24f02a95…e71b
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 0xc52785b9ae…bc08f8
Audit this contract →
← previous block·next block →recent activity