← previous blocknext block →recent activity
Analyzing
Block #101,022,370
21 transactions · 20 stateful · 2026-09-01 10:48:49 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,022,370 · 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
1w02w03w14w05w16w07w08w114w115w216w317w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x97e4c862…4419
0x34b655…2a6f
6 touches
3 conflicts
0xfe45073e…6315
0x34b655…2a6f
6 touches
3 conflicts
0x8488f10f…9354
0x34ae4d…3fc5
4 touches
1 conflict
0xc20bd100…8b0e
0x34ae4d…3fc5
4 touches
1 conflict
0x297de2d5…7396
0x34b655…2a6f
4 touches
1 conflict
0x40f0cbff…df7c
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity