← previous blocknext block →recent activity
Analyzing
Block #101,922,454
14 transactions · 12 stateful · 2026-09-04 14:18:31 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,922,454 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w311w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb856d1a1…1f18
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x6a9e408e97…fb3721
Audit this contract →
← previous block·next block →recent activity