← previous blocknext block →recent activity
Analyzing
Block #101,666,101
14 transactions · 12 stateful · 2026-09-03 16:47:50 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,666,101 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfa805f95…72a4
0x34b655…2a6f
4 touches
1 conflict
0xeb1b66a1…ce4e
0x34b655…2a6f
4 touches
1 conflict
0xe8f860c0…35c9
0x34b655…2a6f
4 touches
1 conflict
0xe4d8dc15…6d1f
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity