← previous blocknext block →recent activity
Analyzing
Block #101,853,143
20 transactions · 18 stateful · 2026-09-04 08:28:38 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,853,143 · 20 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
3w04w16w27w38w411w012w113w214w015w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b6e2a61…3dae
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0xb575cf74…fbd5
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x2b6e2a6185…563dae
Audit this contract →
← previous block·next block →recent activity