← previous blocknext block →recent activity
Analyzing
Block #101,816,687
10 transactions · 9 stateful · 2026-09-04 05:25:15 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,816,687 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71943d07…69fe
0x34b655…2a6f
6 touches
3 conflicts
0x735a86cd…b64d
0x34b655…2a6f
6 touches
3 conflicts
0x76ed17bf…9bd8
0x34b655…2a6f
4 touches
1 conflict
0x18e86f02…fa98
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
2 touches
0 conflicts
0xbb6e8844…f073
0x37db7f…ec7b
2 touches
0 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 0x71943d0702…9069fe
Audit this contract →
← previous block·next block →recent activity