← previous blocknext block →recent activity
Analyzing
Block #99,450,266
20 transactions · 18 stateful · 2026-08-26 22:39:19 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,450,266 · 20 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
1w02w013w014w115w117w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70d81211…f49f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74401d85…ece3
0x34b655…2a6f
4 touches
1 conflict
0x99a9adb7…0804
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
3 conflicts on slot 0x70d812119d…c1f49f
Audit this contract →
← previous block·next block →recent activity