← previous blocknext block →recent activity
Analyzing
Block #101,069,444
21 transactions · 17 stateful · 2026-09-01 14:45:55 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,069,444 · 21 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
1w02w04w05w17w18w213w214w316w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25180879…8191
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xae48911a…f042
0x34b655…2a6f
6 touches
3 conflicts
0x0ec96a42…2743
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x36557a79…cf09
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
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 0x25180879df…1c8191
Audit this contract →
← previous block·next block →recent activity