← previous blocknext block →recent activity
Analyzing
Block #99,172,490
13 transactions · 13 stateful · 2026-08-25 23:21:10 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,172,490 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w49w010w111w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
8 touches
6 conflicts
0x30a112bd…9e41
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x4fb836a6…973e
0x34b655…2a6f
4 touches
1 conflict
0x512368b4…2669
0x34b655…2a6f
4 touches
1 conflict
0x6063145b…03ae
0x34b655…2a6f
4 touches
1 conflict
0x61fe92b6…ee42
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity