← previous blocknext block →recent activity
Analyzing
Block #101,298,818
16 transactions · 14 stateful · 2026-09-02 09:59:55 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,298,818 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w06w07w08w111w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc229cab1…8ffe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4164a01a…1f4a
0x851145…3f07
4 touches
1 conflict
0x6e733b13…b909
0x851145…3f07
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x5a409e7f…09b6
0x34ae4d…3fc5
2 touches
0 conflicts
0x62811193…1869
0x34ae4d…3fc5
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
1 conflict on slot 0xc229cab186…438ffe
Audit this contract →
← previous block·next block →recent activity