← previous blocknext block →recent activity
Analyzing
Block #101,816,550
13 transactions · 13 stateful · 2026-09-04 05:24:34 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,816,550 · 13 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
2w03w04w17w28w210w012w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49299fcf…c552
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd0cd3305…f212
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc395a150…38fa
0x34b655…2a6f
4 touches
1 conflict
0x229c611e…b31a
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
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
6 conflicts on slot 0x49299fcf8b…f1c552
Audit this contract →
← previous block·next block →recent activity