← previous blocknext block →recent activity
Analyzing
Block #101,500,947
25 transactions · 23 stateful · 2026-09-03 02:57:01 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,500,947 · 25 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
1w02w13w219w021w122w023w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb58ed141…c32e
0x34b655…2a6f
6 touches
3 conflicts
0x375a37a1…ac05
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xda50c9d5…674e
0x34b655…2a6f
6 touches
3 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
6 touches
3 conflicts
0x0ffac39e…6d34
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
3 conflicts on slot 0xb58ed141dc…9bc32e
Audit this contract →
← previous block·next block →recent activity