← previous blocknext block →recent activity
Analyzing
Block #101,672,505
64 transactions · 62 stateful · 2026-09-03 17:20:04 UTC
Parallelism
92/100
Blocked
10%
Avg conflicts / tx
0.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,672,505 · 64 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
2w03w04w05w18w111w212w313w463w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
8 touches
6 conflicts
0x382713e8…4417
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x5906754f…b584
0x34b655…2a6f
4 touches
1 conflict
0x7b67f6cf…0aab
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xb1fffc2d…7106
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 0xdbb571e456…b26829
Audit this contract →
← previous block·next block →recent activity