← previous blocknext block →recent activity
Analyzing
Block #101,060,008
15 transactions · 14 stateful · 2026-09-01 13:58:11 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,060,008 · 15 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
1w03w05w16w28w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a5ea2a4…5d55
0x8964d7…10f8
4 touches
1 conflict
0x8a5ea2a4…5d4e
0x8964d7…10f8
4 touches
1 conflict
0x8a5ea2a4…5d4f
0x8964d7…10f8
4 touches
1 conflict
0x8a5ea2a4…5d52
0x8964d7…10f8
4 touches
1 conflict
0x8a5ea2a4…5d53
0x8964d7…10f8
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xaae6463e…bfcc
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x8a5ea2a4c6…c85d55
Audit this contract →
← previous block·next block →recent activity