← previous blocknext block →recent activity
Analyzing
Block #101,965,334
21 transactions · 19 stateful · 2026-09-04 17:56:09 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,965,334 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w39w411w012w113w220w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33b7fbba…64de
0x34b655…2a6f
8 touches
6 conflicts
0xffc921ce…dc0d
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xa62eb46f…89b1
0x34b655…2a6f
6 touches
3 conflicts
0xa7e3ddfa…f0c7
0x34b655…2a6f
6 touches
3 conflicts
0xb3e293fe…be2e
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x33b7fbba1a…5e64de
Audit this contract →
← previous block·next block →recent activity